Hi @DTS Engineer Thanks, we will definitely do, any chance you can share some insights about the bug? like why its happening ? What pattern in swiftui should be avoided to prevent this bug (or any solid proof work around, as our current work around might work for simple projects but not for large complex one), as that issue is blocking us.

@DTS Engineer maybe you have any suggestions?

Hi Wouldn't it be great if that question could be answered in public forum?

ok that's can be handy too but in case WindowGroup embeds a long code can delete ONLY it with its last curly bracket? (basically the opposite of Embed)

Hi, Thanks for your help. Moving my comment to reply

I manage to reproduce: Thread 182: EXC_RESOURCE (RESOURCE_TYPE_MEMORY: high watermark memory limit exceeded) (limit=1450 MB) Which is not exact issue that we have

@DTS Engineer I posted my answer under answers by mistake and not as comment, sorry about that

They are extracting accessibility labels and identifiers and attach it to to the button click analytics, that's how they diff between the events. you can see what they collecting in the page tagging, anyway they responsive on the GitHub so you can always ask them if something doesnt work

I probably missing something BUT if you r a vendor of SDK i.e u ship the SDK for both simulator and device arch and then the customers has a crash on the simulator u won't have an option to symbolize it?